Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 901df8e198f3093b6c585c270c337cd1615cce12bb782604d0fee48e6d50eef1

Tx prefix hash: 798a1c235a060c069d9f28a424c42fe359c9b050c60c32e729718f1c0ae32091
Tx public key: 48af084e40b1eab1c75fc2bf7cba83bbc651046c6c1ab914236a02167e044b20
Timestamp: 1703227135 Timestamp [UCT]: 2023-12-22 06:38:55 Age [y:d:h:m:s]: 01:327:05:45:55
Block: 918496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492730 RingCT/type: yes/0
Extra: 0148af084e40b1eab1c75fc2bf7cba83bbc651046c6c1ab914236a02167e044b200211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55670e2e05fc4c3eb409528d6f58a964d8ae7610c8dc5637efe5fdadb993d7f2 0.600000000000 1376140 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": 918506, "vin": [ { "gen": { "height": 918496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55670e2e05fc4c3eb409528d6f58a964d8ae7610c8dc5637efe5fdadb993d7f2" } } ], "extra": [ 1, 72, 175, 8, 78, 64, 177, 234, 177, 199, 95, 194, 191, 124, 186, 131, 187, 198, 81, 4, 108, 108, 26, 185, 20, 35, 106, 2, 22, 126, 4, 75, 32, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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