Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92af683dbafcf51090b9b90bdec5bb0693be7b5f1559fe241af6decb5ba3e7a7

Tx prefix hash: 927658f57d68a23e9cf903686bf9f6f1fabf4df0b9b0306a1c4fc8a90c587f3a
Tx public key: 7d6b707d4b8f85b0470c21afd89fe289b36c166bf707dae3470a92986c7667f1
Timestamp: 1703215673 Timestamp [UCT]: 2023-12-22 03:27:53 Age [y:d:h:m:s]: 01:321:17:22:14
Block: 918396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488786 RingCT/type: yes/0
Extra: 017d6b707d4b8f85b0470c21afd89fe289b36c166bf707dae3470a92986c7667f10211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2317e2d104693e1d2b7cfa2a7f4d9340b734e703dd285c8024ffda7a0522414 0.600000000000 1376040 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": 918406, "vin": [ { "gen": { "height": 918396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2317e2d104693e1d2b7cfa2a7f4d9340b734e703dd285c8024ffda7a0522414" } } ], "extra": [ 1, 125, 107, 112, 125, 75, 143, 133, 176, 71, 12, 33, 175, 216, 159, 226, 137, 179, 108, 22, 107, 247, 7, 218, 227, 71, 10, 146, 152, 108, 118, 103, 241, 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