Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cff1065ca1c458736bd40122c13c4772752240df3901219035c356c0fecc2b4

Tx prefix hash: 56f750d165bed2ed4236b09982560f45c3542a54fd076454563dea6e99b9a9b7
Tx public key: 2df0063dcdd0dc5be67d788fea8da592548b4021f21c2b8820dde5f315d4da4b
Timestamp: 1700822231 Timestamp [UCT]: 2023-11-24 10:37:11 Age [y:d:h:m:s]: 01:138:13:36:35
Block: 898557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360207 RingCT/type: yes/0
Extra: 012df0063dcdd0dc5be67d788fea8da592548b4021f21c2b8820dde5f315d4da4b02110000000333af99f4000000000000000000

1 output(s) for total of 0.646707110000 dcy

stealth address amount amount idx
00: 1fbeca074eedd0b6dc9a219879994b35c7050db4275d5d2dfd93765b5f0bdbb2 0.646707110000 1354978 of 0

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": 898567, "vin": [ { "gen": { "height": 898557 } } ], "vout": [ { "amount": 646707110, "target": { "key": "1fbeca074eedd0b6dc9a219879994b35c7050db4275d5d2dfd93765b5f0bdbb2" } } ], "extra": [ 1, 45, 240, 6, 61, 205, 208, 220, 91, 230, 125, 120, 143, 234, 141, 165, 146, 84, 139, 64, 33, 242, 28, 43, 136, 32, 221, 229, 243, 21, 212, 218, 75, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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