Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1627caa70902906e1252a44f19c3c6af3da7d72396e685063e42c78b49486e2

Tx prefix hash: 4d79d28aed2dbf6d37462a0f2c97d46da9fa1d67e3210677aaebd6732a24370e
Tx public key: 5d153656f0ced626b15ec9e6c9800b364bc2af9e33be42f6573a341c773769e7
Timestamp: 1705675845 Timestamp [UCT]: 2024-01-19 14:50:45 Age [y:d:h:m:s]: 01:318:06:51:02
Block: 938767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486344 RingCT/type: yes/0
Extra: 015d153656f0ced626b15ec9e6c9800b364bc2af9e33be42f6573a341c773769e702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8afc9a7c36dd53641953ea85328afb07bd589398908e5f2afda17b336d25f88d 0.600000000000 1396845 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": 938777, "vin": [ { "gen": { "height": 938767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8afc9a7c36dd53641953ea85328afb07bd589398908e5f2afda17b336d25f88d" } } ], "extra": [ 1, 93, 21, 54, 86, 240, 206, 214, 38, 177, 94, 201, 230, 201, 128, 11, 54, 75, 194, 175, 158, 51, 190, 66, 246, 87, 58, 52, 28, 119, 55, 105, 231, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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