Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1860719cf9dcce2aa9f9add651abecdce6ebaad767dabdad1532887f96e945e

Tx prefix hash: 7908f893d3b5214a799d2d701264e7df4e8c8cacb41ac2fdad4da8d9e3f2aa4c
Tx public key: 750b7fd91237db0743f06fe391148d21a009f68dc605519a8ee90c7457e029fd
Timestamp: 1695564560 Timestamp [UCT]: 2023-09-24 14:09:20 Age [y:d:h:m:s]: 01:196:13:17:33
Block: 855173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401528 RingCT/type: yes/0
Extra: 01750b7fd91237db0743f06fe391148d21a009f68dc605519a8ee90c7457e029fd021100000002faf35c9c000000000000000000

1 output(s) for total of 0.900444399000 dcy

stealth address amount amount idx
00: 5211217d3d8ee769bf4ac77b89bf10ac09f26f32485c8c2e034633697cd77ff2 0.900444399000 1309179 of 0

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": 855183, "vin": [ { "gen": { "height": 855173 } } ], "vout": [ { "amount": 900444399, "target": { "key": "5211217d3d8ee769bf4ac77b89bf10ac09f26f32485c8c2e034633697cd77ff2" } } ], "extra": [ 1, 117, 11, 127, 217, 18, 55, 219, 7, 67, 240, 111, 227, 145, 20, 141, 33, 160, 9, 246, 141, 198, 5, 81, 154, 142, 233, 12, 116, 87, 224, 41, 253, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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