Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4540373a7a9db51066f69621e9871f40401c4c33e8fd6a4c9b6cc6b357c0003d

Tx prefix hash: e07b108b0f12f46897948d3be7204cc035bd6e221aa918b3bbe89e6cd43152af
Tx public key: dfd5c3d08640c4fa22cc6e9473261ad7374d9e1a412396b7de33123510226cd9
Timestamp: 1703067738 Timestamp [UCT]: 2023-12-20 10:22:18 Age [y:d:h:m:s]: 01:145:04:43:42
Block: 917177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364921 RingCT/type: yes/0
Extra: 01dfd5c3d08640c4fa22cc6e9473261ad7374d9e1a412396b7de33123510226cd902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 682a12148f42d9b537446c4dbacecbcb681cd8cc60e238fb7a63c67bc2de2964 0.600000000000 1374747 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": 917187, "vin": [ { "gen": { "height": 917177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "682a12148f42d9b537446c4dbacecbcb681cd8cc60e238fb7a63c67bc2de2964" } } ], "extra": [ 1, 223, 213, 195, 208, 134, 64, 196, 250, 34, 204, 110, 148, 115, 38, 26, 215, 55, 77, 158, 26, 65, 35, 150, 183, 222, 51, 18, 53, 16, 34, 108, 217, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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