Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaadbd5272efc3ff5564f09e749aa50d84792b06d22dc85883cdc745c83ab44d

Tx prefix hash: 617c414697ad5cdd6c49a90507487b99f9c2c881ea60d7acaa2369e66b4bb3d8
Tx public key: b757dbccc9778acbe014e7771163aaa484c7c2cc07bd04319cd7bff81f6d5fc6
Timestamp: 1694190794 Timestamp [UCT]: 2023-09-08 16:33:14 Age [y:d:h:m:s]: 01:248:01:15:51
Block: 843770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438420 RingCT/type: yes/0
Extra: 01b757dbccc9778acbe014e7771163aaa484c7c2cc07bd04319cd7bff81f6d5fc602110000000575e3f0e9000000000000000000

1 output(s) for total of 0.982290152000 dcy

stealth address amount amount idx
00: a38bf94de07ba4027e9303d3d0a3de3dc822089771fd01c8f784dcfe4b2b78a2 0.982290152000 1297034 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": 843780, "vin": [ { "gen": { "height": 843770 } } ], "vout": [ { "amount": 982290152, "target": { "key": "a38bf94de07ba4027e9303d3d0a3de3dc822089771fd01c8f784dcfe4b2b78a2" } } ], "extra": [ 1, 183, 87, 219, 204, 201, 119, 138, 203, 224, 20, 231, 119, 17, 99, 170, 164, 132, 199, 194, 204, 7, 189, 4, 49, 156, 215, 191, 248, 31, 109, 95, 198, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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