Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 653f96ca109763df0342bb27fe91c55897229a3c1e6d810ecda70667c5e6442c

Tx prefix hash: cb2c89b905a2ff891e0c4310e4cbc38af8801e44d9a4295def383981507c671a
Tx public key: f4fb140644d18257c7947c3373a770cbd77ff399302cfb8e0af759f9720f2ba4
Timestamp: 1703969212 Timestamp [UCT]: 2023-12-30 20:46:52 Age [y:d:h:m:s]: 00:312:16:31:19
Block: 924640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223908 RingCT/type: yes/0
Extra: 01f4fb140644d18257c7947c3373a770cbd77ff399302cfb8e0af759f9720f2ba40211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3dbbd60d6089d9b337ef6665d74dc47a90c9c314a54f1f497a04d2796980fa1a 0.600000000000 1382396 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": 924650, "vin": [ { "gen": { "height": 924640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3dbbd60d6089d9b337ef6665d74dc47a90c9c314a54f1f497a04d2796980fa1a" } } ], "extra": [ 1, 244, 251, 20, 6, 68, 209, 130, 87, 199, 148, 124, 51, 115, 167, 112, 203, 215, 127, 243, 153, 48, 44, 251, 142, 10, 247, 89, 249, 114, 15, 43, 164, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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