Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 677f9b0fb8c721952e5fc46e1fe8d24248c9a3c795cb558194aa09a82f567bd6

Tx prefix hash: ba1e1cd6cdf2cc832b19e286aaa0d3b9cbb7101cabfb601e9838f3cbbc8e52f2
Tx public key: e8ae2a029a9395f1c4be22d6aa041f8ed60ea990e64e783991d11269f3bdf40e
Timestamp: 1703266150 Timestamp [UCT]: 2023-12-22 17:29:10 Age [y:d:h:m:s]: 01:334:09:40:43
Block: 918824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497838 RingCT/type: yes/0
Extra: 01e8ae2a029a9395f1c4be22d6aa041f8ed60ea990e64e783991d11269f3bdf40e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff644c1741dad703e6ea112f93e9417b40beba4e0fbd8b41ff829122b09e92c1 0.600000000000 1376488 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": 918834, "vin": [ { "gen": { "height": 918824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff644c1741dad703e6ea112f93e9417b40beba4e0fbd8b41ff829122b09e92c1" } } ], "extra": [ 1, 232, 174, 42, 2, 154, 147, 149, 241, 196, 190, 34, 214, 170, 4, 31, 142, 214, 14, 169, 144, 230, 78, 120, 57, 145, 209, 18, 105, 243, 189, 244, 14, 2, 17, 0, 0, 0, 1, 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