Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad6be326c0cd3506e75d67fe8de01165efdc945a0ba14bfe4a3a1b83a9c449c3

Tx prefix hash: 4357b972a9e15f180bf4aa3e445c140ee920e4a857c9116f3237bc410a2b91cb
Tx public key: 0bcadaf7cf38d70f1d00fbb5873f2c0abc2896e8e8720b8532d23ca0c287ff3a
Timestamp: 1712906603 Timestamp [UCT]: 2024-04-12 07:23:23 Age [y:d:h:m:s]: 00:361:15:13:31
Block: 998728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258550 RingCT/type: yes/0
Extra: 010bcadaf7cf38d70f1d00fbb5873f2c0abc2896e8e8720b8532d23ca0c287ff3a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7b7868713494e9d5087d8ac866c93a5f869875bbebe0a4d1ab894b7e9df15dc 0.600000000000 1459180 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": 998738, "vin": [ { "gen": { "height": 998728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7b7868713494e9d5087d8ac866c93a5f869875bbebe0a4d1ab894b7e9df15dc" } } ], "extra": [ 1, 11, 202, 218, 247, 207, 56, 215, 15, 29, 0, 251, 181, 135, 63, 44, 10, 188, 40, 150, 232, 232, 114, 11, 133, 50, 210, 60, 160, 194, 135, 255, 58, 2, 17, 0, 0, 0, 2, 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