Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c275326392a16011c1337b3d308cf04d182f3f90d9bcc0d2b0f49cf20b0baf0

Tx prefix hash: bb9c2daa107173c9c5ea59502c060ee0c3d1d14e13f27da94ef89f29536473e3
Tx public key: d71e9527d68523b00394d5023fbd090be3ca3d83556e36f18730c80c2250cbd2
Timestamp: 1701583950 Timestamp [UCT]: 2023-12-03 06:12:30 Age [y:d:h:m:s]: 00:361:08:51:58
Block: 904871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258763 RingCT/type: yes/0
Extra: 01d71e9527d68523b00394d5023fbd090be3ca3d83556e36f18730c80c2250cbd202110000000775e3f0e9000000000000000000

1 output(s) for total of 0.616292274000 dcy

stealth address amount amount idx
00: f8871302571c900962f5d35e26182d25e7f84ab17be619482e901384b44a5170 0.616292274000 1361654 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": 904881, "vin": [ { "gen": { "height": 904871 } } ], "vout": [ { "amount": 616292274, "target": { "key": "f8871302571c900962f5d35e26182d25e7f84ab17be619482e901384b44a5170" } } ], "extra": [ 1, 215, 30, 149, 39, 214, 133, 35, 176, 3, 148, 213, 2, 63, 189, 9, 11, 227, 202, 61, 131, 85, 110, 54, 241, 135, 48, 200, 12, 34, 80, 203, 210, 2, 17, 0, 0, 0, 7, 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