Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7fb1b470934bb2c32bf0395327da91253dbe21ad09edd8e23e2c2e717983eeb

Tx prefix hash: dd88f4a1f39a4ae134a946292747f72e937e099438308f51fcb54e37fbb52796
Tx public key: ef256508578f57f9bda0b024062f6db8995b5059483bdee9a806b8bfe191b062
Timestamp: 1718228369 Timestamp [UCT]: 2024-06-12 21:39:29 Age [y:d:h:m:s]: 01:117:18:46:59
Block: 1042880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342683 RingCT/type: yes/0
Extra: 01ef256508578f57f9bda0b024062f6db8995b5059483bdee9a806b8bfe191b0620211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a29fb7fcab044fff96123cc9c881cf3e85a9e1dee835ee107a8eb4e0816c388 0.600000000000 1511895 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": 1042890, "vin": [ { "gen": { "height": 1042880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a29fb7fcab044fff96123cc9c881cf3e85a9e1dee835ee107a8eb4e0816c388" } } ], "extra": [ 1, 239, 37, 101, 8, 87, 143, 87, 249, 189, 160, 176, 36, 6, 47, 109, 184, 153, 91, 80, 89, 72, 59, 222, 233, 168, 6, 184, 191, 225, 145, 176, 98, 2, 17, 0, 0, 0, 1, 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