Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bfb000d7c35d150913a1d1d2bd0aa1109016311238d33cf70845aa0589f195f

Tx prefix hash: eecbd7537bd111438bef2f6b604254c9ab958e94992a6597859b221d9a5f47ef
Tx public key: 16d0726c6e0d4ca769e8ccbabd2d530b5aebfd4c124783b9457e6ffb1b277852
Timestamp: 1749971527 Timestamp [UCT]: 2025-06-15 07:12:07 Age [y:d:h:m:s]: 00:153:21:18:58
Block: 1305375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107764 RingCT/type: yes/0
Extra: 0116d0726c6e0d4ca769e8ccbabd2d530b5aebfd4c124783b9457e6ffb1b2778520211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b685ea3511939b2dc8f1ecc1c98d4bfe8238059983a108c0843bb3ff1d281f43 0.600000000000 1792974 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": 1305385, "vin": [ { "gen": { "height": 1305375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b685ea3511939b2dc8f1ecc1c98d4bfe8238059983a108c0843bb3ff1d281f43" } } ], "extra": [ 1, 22, 208, 114, 108, 110, 13, 76, 167, 105, 232, 204, 186, 189, 45, 83, 11, 90, 235, 253, 76, 18, 71, 131, 185, 69, 126, 111, 251, 27, 39, 120, 82, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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