Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cab83bfe94ee8c5736dd7038f46b5ccab8e1453e061ae0c00144bc1a907436d

Tx prefix hash: 6162c0d688e42b06cd224115606f11ec4d6c13095f2ecc0250a0ae2453a4244f
Tx public key: d3495e84d97cbbcec981f4b0415a313658a68764ff7ff03befc4115ea4acbbb3
Timestamp: 1711535850 Timestamp [UCT]: 2024-03-27 10:37:30 Age [y:d:h:m:s]: 01:012:07:44:34
Block: 987406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269744 RingCT/type: yes/0
Extra: 01d3495e84d97cbbcec981f4b0415a313658a68764ff7ff03befc4115ea4acbbb30211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a50a52ca7e97531cdc7f225cb6a8ca49b0509c3e54cf9d3b7ed5dcd284702f3 0.600000000000 1447655 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": 987416, "vin": [ { "gen": { "height": 987406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a50a52ca7e97531cdc7f225cb6a8ca49b0509c3e54cf9d3b7ed5dcd284702f3" } } ], "extra": [ 1, 211, 73, 94, 132, 217, 124, 187, 206, 201, 129, 244, 176, 65, 90, 49, 54, 88, 166, 135, 100, 255, 127, 240, 59, 239, 196, 17, 94, 164, 172, 187, 179, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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