Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5b30f148bf4ce76cea023c2953909ecbdb7500056b3ddb83b16c18492dab778

Tx prefix hash: aee7747dcf0d35650c1d990ac82d461d8fcc4d4d74493b6e983f238a66917d32
Tx public key: c24e41ff147096d4c3bd01a64f251bd1f2f64d4c7a2650c26faf9b20a4110cd5
Timestamp: 1698740188 Timestamp [UCT]: 2023-10-31 08:16:28 Age [y:d:h:m:s]: 01:160:23:02:09
Block: 881512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376036 RingCT/type: yes/0
Extra: 01c24e41ff147096d4c3bd01a64f251bd1f2f64d4c7a2650c26faf9b20a4110cd502110000000475e3f0e9000000000000000000

1 output(s) for total of 0.736520470000 dcy

stealth address amount amount idx
00: 1f07ada4bb71f4c3b3f8cb9d8995dc41f17fb38ce3cdf38c132c201aa73f6aa6 0.736520470000 1337104 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": 881522, "vin": [ { "gen": { "height": 881512 } } ], "vout": [ { "amount": 736520470, "target": { "key": "1f07ada4bb71f4c3b3f8cb9d8995dc41f17fb38ce3cdf38c132c201aa73f6aa6" } } ], "extra": [ 1, 194, 78, 65, 255, 20, 112, 150, 212, 195, 189, 1, 166, 79, 37, 27, 209, 242, 246, 77, 76, 122, 38, 80, 194, 111, 175, 155, 32, 164, 17, 12, 213, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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