Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b62b951b044340a9a70e35b87c9dc9f2382c58ff0a48c8390de0624de8498b68

Tx prefix hash: 3ddc35f32e2999f0e8ece5817da976ad65dde21b874ac7fababa8b7ae9b26666
Tx public key: 5acc9c88e945cf618e867db53a4d4e9acd00c630c636b2154033ca24e3dfb207
Timestamp: 1750286184 Timestamp [UCT]: 2025-06-18 22:36:24 Age [y:d:h:m:s]: 00:154:19:08:21
Block: 1307949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108440 RingCT/type: yes/0
Extra: 015acc9c88e945cf618e867db53a4d4e9acd00c630c636b2154033ca24e3dfb20702110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8f6f32eea29746e286199a43465bab9b1cf8b1ed210104afbbbab1d07bc53bb 0.600000000000 1795560 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": 1307959, "vin": [ { "gen": { "height": 1307949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8f6f32eea29746e286199a43465bab9b1cf8b1ed210104afbbbab1d07bc53bb" } } ], "extra": [ 1, 90, 204, 156, 136, 233, 69, 207, 97, 142, 134, 125, 181, 58, 77, 78, 154, 205, 0, 198, 48, 198, 54, 178, 21, 64, 51, 202, 36, 227, 223, 178, 7, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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