Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57e794fe015d4c27835363b66d66b716a8e9566674d80e3867d1ffb616c74313

Tx prefix hash: e01fbd1da11c7d26f222b5ccd04096a71f7e917f5f86853b47bd6269f3e42df3
Tx public key: dd79c0c1fab892d7fbda389995740f6037bddffab6701c5afbc765ddfb872a30
Timestamp: 1709794501 Timestamp [UCT]: 2024-03-07 06:55:01 Age [y:d:h:m:s]: 01:086:14:16:38
Block: 972953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322925 RingCT/type: yes/0
Extra: 01dd79c0c1fab892d7fbda389995740f6037bddffab6701c5afbc765ddfb872a300211000000023f82f9fb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 818866296364c3d1e2a4e638761408caacf8624ffc5229bfcfe6e618e01f8756 0.600000000000 1432878 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": 972963, "vin": [ { "gen": { "height": 972953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "818866296364c3d1e2a4e638761408caacf8624ffc5229bfcfe6e618e01f8756" } } ], "extra": [ 1, 221, 121, 192, 193, 250, 184, 146, 215, 251, 218, 56, 153, 149, 116, 15, 96, 55, 189, 223, 250, 182, 112, 28, 90, 251, 199, 101, 221, 251, 135, 42, 48, 2, 17, 0, 0, 0, 2, 63, 130, 249, 251, 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