Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccb891ee40c2425899b06001119adf4bf6a7183ce6487f3d9fd62ab1a0cf79a3

Tx prefix hash: 624508d156a35cb96d7be91427c895227f6c16dbdbd405ebcc6c9c8014aeb81d
Tx public key: 90e5d0147e47a5dbfa5d4de37ac53519e20b54610848a144776c4770c53c1aef
Timestamp: 1709903341 Timestamp [UCT]: 2024-03-08 13:09:01 Age [y:d:h:m:s]: 01:252:13:19:09
Block: 973860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439219 RingCT/type: yes/0
Extra: 0190e5d0147e47a5dbfa5d4de37ac53519e20b54610848a144776c4770c53c1aef02110000001152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cff82e0b75df6bb7ad5929b258805b846c3730b22180362ae4b3071194f6a7e 0.600000000000 1433801 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": 973870, "vin": [ { "gen": { "height": 973860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cff82e0b75df6bb7ad5929b258805b846c3730b22180362ae4b3071194f6a7e" } } ], "extra": [ 1, 144, 229, 208, 20, 126, 71, 165, 219, 250, 93, 77, 227, 122, 197, 53, 25, 226, 11, 84, 97, 8, 72, 161, 68, 119, 108, 71, 112, 197, 60, 26, 239, 2, 17, 0, 0, 0, 17, 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