Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad327737960c097c5f0f1b3dada74146ef1fad75b0bc6e68b581c86b7f05b7c0

Tx prefix hash: 490d7de7d3d0f22f278d4a5cb135311f0fe462c905571547ca83f1679b07017e
Tx public key: f88d724199f1f7fe20ea7bb3fdbf69f3ee0a8a1b0d38a6475405abff1117f0b7
Timestamp: 1657812182 Timestamp [UCT]: 2022-07-14 15:23:02 Age [y:d:h:m:s]: 02:141:15:13:47
Block: 543656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 622588 RingCT/type: yes/0
Extra: 01f88d724199f1f7fe20ea7bb3fdbf69f3ee0a8a1b0d38a6475405abff1117f0b702110000000d5eb576c5000000000000000000

1 output(s) for total of 9.697105738000 dcy

stealth address amount amount idx
00: 1f608d148328f3fea23da3318e08a25715e231fb44b99ccfd1e068367dd15779 9.697105738000 974347 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": 543666, "vin": [ { "gen": { "height": 543656 } } ], "vout": [ { "amount": 9697105738, "target": { "key": "1f608d148328f3fea23da3318e08a25715e231fb44b99ccfd1e068367dd15779" } } ], "extra": [ 1, 248, 141, 114, 65, 153, 241, 247, 254, 32, 234, 123, 179, 253, 191, 105, 243, 238, 10, 138, 27, 13, 56, 166, 71, 84, 5, 171, 255, 17, 23, 240, 183, 2, 17, 0, 0, 0, 13, 94, 181, 118, 197, 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