Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: fdbd7349fcede53174dca9fef09736e23af5df489c0b418d9f754bb1c365b72e

Tx prefix hash: d7368b78eda1d51341df7456f41c17cf0046c0916233b5baf0678885233d2897
Tx public key: 571347d35cb5e9c3430a46f5c261cb4017a6f18d26cce1b1f2960447a85b0400
Timestamp: 1745333723 Timestamp [UCT]: 2025-04-22 14:55:23 Age [y:d:h:m:s]: 00:277:12:44:52
Block: 1267065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195990 RingCT/type: yes/0
Extra: 01571347d35cb5e9c3430a46f5c261cb4017a6f18d26cce1b1f2960447a85b04000211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7fa76f876f246fbb7605aa38b63c983af8935eadf503e6b7b382a9112e7de55 0.600000000000 1754290 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1267075, "vin": [ { "gen": { "height": 1267065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7fa76f876f246fbb7605aa38b63c983af8935eadf503e6b7b382a9112e7de55" } } ], "extra": [ 1, 87, 19, 71, 211, 92, 181, 233, 195, 67, 10, 70, 245, 194, 97, 203, 64, 23, 166, 241, 141, 38, 204, 225, 177, 242, 150, 4, 71, 168, 91, 4, 0, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8