Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbde0cb7af7d9e4fcf2811fe1c4ce1508bfa74e33ddb44e9b43a382977832b07

Tx prefix hash: 2d287013a1e4fcc7a18751097284c6c9f01fa244b7952024011cb7b870b7e896
Tx public key: 9575c73d9701ffb5259cbaee1302530d1cb0103f9ab5e10c49b3fac6cbe24636
Timestamp: 1761056505 Timestamp [UCT]: 2025-10-21 14:21:45 Age [y:d:h:m:s]: 00:019:23:42:45
Block: 1394830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14296 RingCT/type: yes/0
Extra: 019575c73d9701ffb5259cbaee1302530d1cb0103f9ab5e10c49b3fac6cbe24636021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 102c87692738c6c740fe2b9a0fc4d4106b3fa1f09112476d52f6c0df07c23706 0.600000000000 1883105 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": 1394840, "vin": [ { "gen": { "height": 1394830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "102c87692738c6c740fe2b9a0fc4d4106b3fa1f09112476d52f6c0df07c23706" } } ], "extra": [ 1, 149, 117, 199, 61, 151, 1, 255, 181, 37, 156, 186, 238, 19, 2, 83, 13, 28, 176, 16, 63, 154, 181, 225, 12, 73, 179, 250, 198, 203, 226, 70, 54, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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