Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43f8b16b96c89a8946dae0bb60d68670009c76a394cd0a55095656298efb7488

Tx prefix hash: c0f3957ae9d78998a62781c48696b3fe70073f1889591bbc7edd02ba8a0418d2
Tx public key: c4897c0338a8e901200f50728ef3d5d824fdeff4d1f5b2e8febe7195c24bf50d
Timestamp: 1701347020 Timestamp [UCT]: 2023-11-30 12:23:40 Age [y:d:h:m:s]: 01:086:00:59:04
Block: 902900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322617 RingCT/type: yes/0
Extra: 01c4897c0338a8e901200f50728ef3d5d824fdeff4d1f5b2e8febe7195c24bf50d021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.625629859000 dcy

stealth address amount amount idx
00: 453c63daa100f093d322e356a8bb117f53faedc00135b0af42daf4d096c938ba 0.625629859000 1359563 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": 902910, "vin": [ { "gen": { "height": 902900 } } ], "vout": [ { "amount": 625629859, "target": { "key": "453c63daa100f093d322e356a8bb117f53faedc00135b0af42daf4d096c938ba" } } ], "extra": [ 1, 196, 137, 124, 3, 56, 168, 233, 1, 32, 15, 80, 114, 142, 243, 213, 216, 36, 253, 239, 244, 209, 245, 178, 232, 254, 190, 113, 149, 194, 75, 245, 13, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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