Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efdbdebf062c3173065103f9751002e825bae56590709e24c322a45ad80235c5

Tx prefix hash: 9bc7f2225b0ae87f048746f53f40d3584748b17f27012c1bb69e20c2b3b9deef
Tx public key: 0a5362d60edafe7ad5e7214b7e009349c8bf13b571e5337a8f6efb63f9cd3fd8
Timestamp: 1725996831 Timestamp [UCT]: 2024-09-10 19:33:51 Age [y:d:h:m:s]: 00:165:01:30:29
Block: 1107281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117760 RingCT/type: yes/0
Extra: 010a5362d60edafe7ad5e7214b7e009349c8bf13b571e5337a8f6efb63f9cd3fd802110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4887f52b5e8ed54fdebdc9b63cc8a4b78e21259be6aad3000b49b61399dbefa7 0.600000000000 1584892 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": 1107291, "vin": [ { "gen": { "height": 1107281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4887f52b5e8ed54fdebdc9b63cc8a4b78e21259be6aad3000b49b61399dbefa7" } } ], "extra": [ 1, 10, 83, 98, 214, 14, 218, 254, 122, 213, 231, 33, 75, 126, 0, 147, 73, 200, 191, 19, 181, 113, 229, 51, 122, 143, 110, 251, 99, 249, 205, 63, 216, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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