Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cd1d4cbee0a0416359dac9800f75f54e45e9d87094aceafe21d37a9ca22f0ea

Tx prefix hash: b01d3fdbe8b73dfe4486c09b0c79e13721f76ffda1e0a98dd557086581154336
Tx public key: 191d3fb5836541f38fd2d9440af2001322de9921f5d2d985bcdff1fe8dee1f57
Timestamp: 1738257235 Timestamp [UCT]: 2025-01-30 17:13:55 Age [y:d:h:m:s]: 00:042:19:20:07
Block: 1208492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30640 RingCT/type: yes/0
Extra: 01191d3fb5836541f38fd2d9440af2001322de9921f5d2d985bcdff1fe8dee1f570211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94f304f5c6ff920994c6de572c5d2d623a7a81db943912f9bd8c42c5e027ad37 0.600000000000 1695225 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": 1208502, "vin": [ { "gen": { "height": 1208492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94f304f5c6ff920994c6de572c5d2d623a7a81db943912f9bd8c42c5e027ad37" } } ], "extra": [ 1, 25, 29, 63, 181, 131, 101, 65, 243, 143, 210, 217, 68, 10, 242, 0, 19, 34, 222, 153, 33, 245, 210, 217, 133, 188, 223, 241, 254, 141, 238, 31, 87, 2, 17, 0, 0, 0, 7, 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