Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f62f9e15954910f272d9d7e9205f8057af8ce71f63eb1be2a465ed04d84d197

Tx prefix hash: b6e20e4ffe1f57b528352bb89fe1e3a1423891788e2f44c28949aa2016af7c6d
Tx public key: 1bca5d47c046d4c27c2a9f09034be4880ebe4fc3ab6e623ef5acb487f603e887
Timestamp: 1746403458 Timestamp [UCT]: 2025-05-05 00:04:18 Age [y:d:h:m:s]: 00:196:22:01:07
Block: 1275927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138446 RingCT/type: yes/0
Extra: 011bca5d47c046d4c27c2a9f09034be4880ebe4fc3ab6e623ef5acb487f603e887021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 403892cd87e9fcf0734518c178f1eafa72dba9be0b63069e2a8c9e453469a1f5 0.600000000000 1763242 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": 1275937, "vin": [ { "gen": { "height": 1275927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "403892cd87e9fcf0734518c178f1eafa72dba9be0b63069e2a8c9e453469a1f5" } } ], "extra": [ 1, 27, 202, 93, 71, 192, 70, 212, 194, 124, 42, 159, 9, 3, 75, 228, 136, 14, 190, 79, 195, 171, 110, 98, 62, 245, 172, 180, 135, 246, 3, 232, 135, 2, 17, 0, 0, 0, 2, 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