Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47f48f1241cb9ff2cc6037b487cd3c349e98a201e4906cdd617b2fe71ddd16d6

Tx prefix hash: ee8f9a7b1172b5aac402ae5761ec7de20c9f2b43eaebebbcd9f40fec71a8d7db
Tx public key: 97a8f43d7eb989185897b8e096ba0c2e5bd3286278384ef32059c44b175a64cb
Timestamp: 1706105856 Timestamp [UCT]: 2024-01-24 14:17:36 Age [y:d:h:m:s]: 01:056:08:54:36
Block: 942337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301403 RingCT/type: yes/0
Extra: 0197a8f43d7eb989185897b8e096ba0c2e5bd3286278384ef32059c44b175a64cb02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 374dcc045a5178df65622a4945ef7bbeab1f7016f02cf21d1b7c8e3c07bb05a5 0.600000000000 1400507 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": 942347, "vin": [ { "gen": { "height": 942337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "374dcc045a5178df65622a4945ef7bbeab1f7016f02cf21d1b7c8e3c07bb05a5" } } ], "extra": [ 1, 151, 168, 244, 61, 126, 185, 137, 24, 88, 151, 184, 224, 150, 186, 12, 46, 91, 211, 40, 98, 120, 56, 78, 243, 32, 89, 196, 75, 23, 90, 100, 203, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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