Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e628395ab88853785b47b22ef9ffce5430af5a947b85c4e87af8145f8db6f311

Tx prefix hash: e99510e64d35962119e3c5b48debbed016b71b7a2abcc0dba7b60efe85e76488
Tx public key: f21b0e7df30a208539e5aae7ecc9923455f888d25604b55b7756d8d25e0a06da
Timestamp: 1716905565 Timestamp [UCT]: 2024-05-28 14:12:45 Age [y:d:h:m:s]: 00:337:15:18:42
Block: 1031915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241301 RingCT/type: yes/0
Extra: 01f21b0e7df30a208539e5aae7ecc9923455f888d25604b55b7756d8d25e0a06da02110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7454cf2389b148bf06598d0d084d9804a2c44f32ad14d91f87618f8ca631afc7 0.600000000000 1500364 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": 1031925, "vin": [ { "gen": { "height": 1031915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7454cf2389b148bf06598d0d084d9804a2c44f32ad14d91f87618f8ca631afc7" } } ], "extra": [ 1, 242, 27, 14, 125, 243, 10, 32, 133, 57, 229, 170, 231, 236, 201, 146, 52, 85, 248, 136, 210, 86, 4, 181, 91, 119, 86, 216, 210, 94, 10, 6, 218, 2, 17, 0, 0, 0, 13, 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