Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 852ee78f748e7c7bacc6bcd4adb9f40829cd676542cb3f59811a24e0562f4541

Tx prefix hash: a155f6e90b1dae964ae3bdb8fd7f578dfb9c807eaca477508be28aa03b64c015
Tx public key: 484b9545d5e051686553899d797bec8f9ff27c3dd5a7e16775e41b05d1e8c145
Timestamp: 1719494834 Timestamp [UCT]: 2024-06-27 13:27:14 Age [y:d:h:m:s]: 00:262:21:49:45
Block: 1053363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187875 RingCT/type: yes/0
Extra: 01484b9545d5e051686553899d797bec8f9ff27c3dd5a7e16775e41b05d1e8c1450211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe80c3532cab7e472de5e6cae39f14490bbd9e4907c7801fc364cd0ed6072316 0.600000000000 1523710 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": 1053373, "vin": [ { "gen": { "height": 1053363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe80c3532cab7e472de5e6cae39f14490bbd9e4907c7801fc364cd0ed6072316" } } ], "extra": [ 1, 72, 75, 149, 69, 213, 224, 81, 104, 101, 83, 137, 157, 121, 123, 236, 143, 159, 242, 124, 61, 213, 167, 225, 103, 117, 228, 27, 5, 209, 232, 193, 69, 2, 17, 0, 0, 0, 2, 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