Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06e1457dd2d99d06dbefe82bcaedb8e2435401f607989823cf6ce05694ac911c

Tx prefix hash: 1290433728234d5c878f965a45342b4618063955b933521564ad665b411a0b9f
Tx public key: 7b820fa5acb27af910d51ee9c3c1d968240071bfc5743f7a9c9e0be0ee8e8e1b
Timestamp: 1756965251 Timestamp [UCT]: 2025-09-04 05:54:11 Age [y:d:h:m:s]: 00:110:10:29:00
Block: 1360978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78993 RingCT/type: yes/0
Extra: 017b820fa5acb27af910d51ee9c3c1d968240071bfc5743f7a9c9e0be0ee8e8e1b021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70c8272e6423d92de1eabe4f2c0b5cdd53623709969f551a7bfcab1f25a176bd 0.600000000000 1848991 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": 1360988, "vin": [ { "gen": { "height": 1360978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70c8272e6423d92de1eabe4f2c0b5cdd53623709969f551a7bfcab1f25a176bd" } } ], "extra": [ 1, 123, 130, 15, 165, 172, 178, 122, 249, 16, 213, 30, 233, 195, 193, 217, 104, 36, 0, 113, 191, 197, 116, 63, 122, 156, 158, 11, 224, 238, 142, 142, 27, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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