Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e934fe9a9afdcd4b77cf75060c59709a5aa995b06380ac26e0f89b66d25552ba

Tx prefix hash: 13e7dc53839dce9d0992bcd147054f82cf59d74283010baaa8d093304af2d6e3
Tx public key: 0452c59dfafa5fccc4282a7baa6b0e9d042795603d04ca56ff0dcc4c279a5f40
Timestamp: 1708563799 Timestamp [UCT]: 2024-02-22 01:03:19 Age [y:d:h:m:s]: 00:323:07:34:45
Block: 962742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231451 RingCT/type: yes/0
Extra: 010452c59dfafa5fccc4282a7baa6b0e9d042795603d04ca56ff0dcc4c279a5f4002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b2b93f444d0a26abbd63db1fa966c7b0a4e366438c90c35d0b82a401d88f841 0.600000000000 1422425 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": 962752, "vin": [ { "gen": { "height": 962742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b2b93f444d0a26abbd63db1fa966c7b0a4e366438c90c35d0b82a401d88f841" } } ], "extra": [ 1, 4, 82, 197, 157, 250, 250, 95, 204, 196, 40, 42, 123, 170, 107, 14, 157, 4, 39, 149, 96, 61, 4, 202, 86, 255, 13, 204, 76, 39, 154, 95, 64, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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