Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03c5640826bf202c0c29c72e7132a2807145de0f3a0a8eca46c05a18c5aca9ce

Tx prefix hash: 08797a9b9df160a84a188a74b8acdfa38e666da14b062b86afcf857be1fb0d70
Tx public key: f63e679869905da3043ae7434365dc825cdf4081c9d1e5cf995e1b4e6af162fe
Timestamp: 1702327636 Timestamp [UCT]: 2023-12-11 20:47:16 Age [y:d:h:m:s]: 01:336:21:31:59
Block: 911050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499635 RingCT/type: yes/0
Extra: 01f63e679869905da3043ae7434365dc825cdf4081c9d1e5cf995e1b4e6af162fe02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 091e1c2f71bf1c660448b985342812756d65d5ca41d8e6e85b9e1e284467f04f 0.600000000000 1368225 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": 911060, "vin": [ { "gen": { "height": 911050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "091e1c2f71bf1c660448b985342812756d65d5ca41d8e6e85b9e1e284467f04f" } } ], "extra": [ 1, 246, 62, 103, 152, 105, 144, 93, 163, 4, 58, 231, 67, 67, 101, 220, 130, 92, 223, 64, 129, 201, 209, 229, 207, 153, 94, 27, 78, 106, 241, 98, 254, 2, 17, 0, 0, 0, 3, 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