Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 571a7d68bf717b1fc87b842588599149348d3b4163ec86f140a707c11f9948bf

Tx prefix hash: fd036fc85a12871d9e540ba1c480c8b7f380b589963fda0fcc6cfbf2f69e9a2d
Tx public key: e6a08274a4efa3687def3cf2dac6c7c818cd340692367085e6d6c686ced32944
Timestamp: 1731093487 Timestamp [UCT]: 2024-11-08 19:18:07 Age [y:d:h:m:s]: 00:133:21:02:03
Block: 1149449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95502 RingCT/type: yes/0
Extra: 01e6a08274a4efa3687def3cf2dac6c7c818cd340692367085e6d6c686ced32944021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7234ee485fa5a5a8e36c01096c4f5fba8f4f2653fd3c60da7dda66a0fb7da48 0.600000000000 1634528 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": 1149459, "vin": [ { "gen": { "height": 1149449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7234ee485fa5a5a8e36c01096c4f5fba8f4f2653fd3c60da7dda66a0fb7da48" } } ], "extra": [ 1, 230, 160, 130, 116, 164, 239, 163, 104, 125, 239, 60, 242, 218, 198, 199, 200, 24, 205, 52, 6, 146, 54, 112, 133, 230, 214, 198, 134, 206, 211, 41, 68, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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