Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7e963800d2a036cce2f519dd4c4846d637f956207c032d66d42c9ab5f07f8bf

Tx prefix hash: 8c0054a6f89928562feff9e50238ef1a0530134ebb432d7f53961b3a84e26462
Tx public key: 757626241ea34e9a9fc259609b6bebc39bb9e94838e7f59c8579b04cf01ee3e0
Timestamp: 1711380594 Timestamp [UCT]: 2024-03-25 15:29:54 Age [y:d:h:m:s]: 01:007:23:38:03
Block: 986119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266656 RingCT/type: yes/0
Extra: 01757626241ea34e9a9fc259609b6bebc39bb9e94838e7f59c8579b04cf01ee3e00211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68682b3ea3e5a3b387b08a4258cb335c4538e31495682b6e10272bbbff0833c4 0.600000000000 1446346 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": 986129, "vin": [ { "gen": { "height": 986119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68682b3ea3e5a3b387b08a4258cb335c4538e31495682b6e10272bbbff0833c4" } } ], "extra": [ 1, 117, 118, 38, 36, 30, 163, 78, 154, 159, 194, 89, 96, 155, 107, 235, 195, 155, 185, 233, 72, 56, 231, 245, 156, 133, 121, 176, 76, 240, 30, 227, 224, 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