Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acdfe641799a53bfb5104a230a5630f0b71082f5e3ddd57c41959f39aa8ead7d

Tx prefix hash: 334ae59730c065fb32949065b3ce140582a0a2199ed583c7b47c5333f682a63d
Tx public key: 1dee237c0005f640a664b8b0b7c16cbe4a7d66b0d0948a9e1e0647a09773fb36
Timestamp: 1735049828 Timestamp [UCT]: 2024-12-24 14:17:08 Age [y:d:h:m:s]: 00:095:16:33:12
Block: 1182217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68160 RingCT/type: yes/0
Extra: 011dee237c0005f640a664b8b0b7c16cbe4a7d66b0d0948a9e1e0647a09773fb360211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a99d455ef37aa2446e0269c8659ade6c4920ef9d9235908427dfa1e6ff75c72 0.600000000000 1668650 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": 1182227, "vin": [ { "gen": { "height": 1182217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a99d455ef37aa2446e0269c8659ade6c4920ef9d9235908427dfa1e6ff75c72" } } ], "extra": [ 1, 29, 238, 35, 124, 0, 5, 246, 64, 166, 100, 184, 176, 183, 193, 108, 190, 74, 125, 102, 176, 208, 148, 138, 158, 30, 6, 71, 160, 151, 115, 251, 54, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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