Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d4bfee3b9e658473fdf2d83b9a9bdaf0245c3f34bf822d0be684bb386f57c30

Tx prefix hash: 11ece953617540c8bcbfb65316f065b3115c05faad79850d055ae5cca0bf26f7
Tx public key: 55875f61e40a7513226e094e3c40a058f90deae13c7a109d5d37e546bb39655b
Timestamp: 1697075737 Timestamp [UCT]: 2023-10-12 01:55:37 Age [y:d:h:m:s]: 01:181:10:45:14
Block: 867702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390720 RingCT/type: yes/0
Extra: 0155875f61e40a7513226e094e3c40a058f90deae13c7a109d5d37e546bb39655b021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.818357571000 dcy

stealth address amount amount idx
00: f29d58eb93216296eeba99cd521d5ff584ec0d1d1543643774814624862cf9ac 0.818357571000 1322410 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": 867712, "vin": [ { "gen": { "height": 867702 } } ], "vout": [ { "amount": 818357571, "target": { "key": "f29d58eb93216296eeba99cd521d5ff584ec0d1d1543643774814624862cf9ac" } } ], "extra": [ 1, 85, 135, 95, 97, 228, 10, 117, 19, 34, 110, 9, 78, 60, 64, 160, 88, 249, 13, 234, 225, 60, 122, 16, 157, 93, 55, 229, 70, 187, 57, 101, 91, 2, 17, 0, 0, 0, 1, 230, 210, 127, 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