Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db2c38ca4138921eb269afb56d11184e886cf7139b9e0cb2ced3611f4266dd55

Tx prefix hash: 8ac86dd7057f84d0e4570be53e8ad9b4e1e2871f7b6c6ebf03d74698df4ff38e
Tx public key: 09734c8ca803abd5cbf7318194526fa1c1ef73b07ef13edea2c5a10f8912c9dd
Timestamp: 1582936101 Timestamp [UCT]: 2020-02-29 00:28:21 Age [y:d:h:m:s]: 04:346:12:25:45
Block: 73702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1141100 RingCT/type: yes/0
Extra: 0109734c8ca803abd5cbf7318194526fa1c1ef73b07ef13edea2c5a10f8912c9dd0211000000168a2ee0d9000000000000000000

1 output(s) for total of 349.780406406000 dcy

stealth address amount amount idx
00: 1168cfe33f138f59304f9e51995fd6ee7a3ec96bf8af125302312ebdbacc6ae8 349.780406406000 136022 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": 73712, "vin": [ { "gen": { "height": 73702 } } ], "vout": [ { "amount": 349780406406, "target": { "key": "1168cfe33f138f59304f9e51995fd6ee7a3ec96bf8af125302312ebdbacc6ae8" } } ], "extra": [ 1, 9, 115, 76, 140, 168, 3, 171, 213, 203, 247, 49, 129, 148, 82, 111, 161, 193, 239, 115, 176, 126, 241, 62, 222, 162, 197, 161, 15, 137, 18, 201, 221, 2, 17, 0, 0, 0, 22, 138, 46, 224, 217, 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