Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a518d842883edc70e140bb898d7e0965282c04d5bec4f1cbaee5d75f44bae390

Tx prefix hash: 2e3b59514a2167f872ccd122973368a3a2debb51bca0ce2ea193cafd39a233a2
Tx public key: b2da13c86acc96beb71cf31fabd4b51d2fe3f3b20cc0c9b73a02186bea1bf254
Timestamp: 1711469117 Timestamp [UCT]: 2024-03-26 16:05:17 Age [y:d:h:m:s]: 01:047:07:08:17
Block: 986858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294764 RingCT/type: yes/0
Extra: 01b2da13c86acc96beb71cf31fabd4b51d2fe3f3b20cc0c9b73a02186bea1bf25402110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30bdb9e2c8bf682446bf7b675a445adbcaa98450f17f6238c77739f476400cdc 0.600000000000 1447093 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": 986868, "vin": [ { "gen": { "height": 986858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30bdb9e2c8bf682446bf7b675a445adbcaa98450f17f6238c77739f476400cdc" } } ], "extra": [ 1, 178, 218, 19, 200, 106, 204, 150, 190, 183, 28, 243, 31, 171, 212, 181, 29, 47, 227, 243, 178, 12, 192, 201, 183, 58, 2, 24, 107, 234, 27, 242, 84, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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