Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57b1d974a4bdfbc697b230c6fcb07f6504981d8bcde3c77ab1ebdea0fe477e24

Tx prefix hash: b341c2beb9f48b26819a3f7c3bc180a5fa6d02ded53c4931e3f2861c84d5b1a4
Tx public key: 2a5e57eb4dbbfb47db10e4df75d3cb1d64d2d15d283dd4ca630cd10aa9303718
Timestamp: 1706412195 Timestamp [UCT]: 2024-01-28 03:23:15 Age [y:d:h:m:s]: 01:293:01:10:11
Block: 944879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468260 RingCT/type: yes/0
Extra: 012a5e57eb4dbbfb47db10e4df75d3cb1d64d2d15d283dd4ca630cd10aa930371802110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e5e7cc901687f8957f5a6d87f59790e77d91b201ff951d18559860d56d7e9cc 0.600000000000 1403171 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": 944889, "vin": [ { "gen": { "height": 944879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e5e7cc901687f8957f5a6d87f59790e77d91b201ff951d18559860d56d7e9cc" } } ], "extra": [ 1, 42, 94, 87, 235, 77, 187, 251, 71, 219, 16, 228, 223, 117, 211, 203, 29, 100, 210, 209, 93, 40, 61, 212, 202, 99, 12, 209, 10, 169, 48, 55, 24, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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