Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2934b17f0dcc2df141f04dfafa69bba31d1f85e4ef35a1202741f75db125cfc6

Tx prefix hash: 41da7141fa608da4ae4743540c8c8ff9c93c465cfd592ebc90cd6bde0d44bbf5
Tx public key: ec20fc30a47b611de4d1dad9f1a7bc8e99381ccac1d00644b1c61a38dc1faded
Timestamp: 1761693157 Timestamp [UCT]: 2025-10-28 23:12:37 Age [y:d:h:m:s]: 00:014:11:58:09
Block: 1400106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10367 RingCT/type: yes/0
Extra: 01ec20fc30a47b611de4d1dad9f1a7bc8e99381ccac1d00644b1c61a38dc1faded021100000004df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf712f0fe23db4567a3c5d51ff36fdb1ed72d5dee08b3dcc5d269bbd76f636eb 0.600000000000 1888413 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": 1400116, "vin": [ { "gen": { "height": 1400106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf712f0fe23db4567a3c5d51ff36fdb1ed72d5dee08b3dcc5d269bbd76f636eb" } } ], "extra": [ 1, 236, 32, 252, 48, 164, 123, 97, 29, 228, 209, 218, 217, 241, 167, 188, 142, 153, 56, 28, 202, 193, 208, 6, 68, 177, 198, 26, 56, 220, 31, 173, 237, 2, 17, 0, 0, 0, 4, 223, 90, 36, 122, 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