Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c763b96a7e02b6583c0ceaaa1961943c1f7ca220542b1e998cff502ade10db5b

Tx prefix hash: 8f176b876ec86ddf21294f6dc7ee71131358dce6aec3ecf4d705f9c3fae27c99
Tx public key: 1a2a31215e2f839a32a88bfdb0bd65e62ad4fc3a9b116468fe86f5306c1da75b
Timestamp: 1707562083 Timestamp [UCT]: 2024-02-10 10:48:03 Age [y:d:h:m:s]: 01:268:19:56:06
Block: 954430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450891 RingCT/type: yes/0
Extra: 011a2a31215e2f839a32a88bfdb0bd65e62ad4fc3a9b116468fe86f5306c1da75b0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac091300dcdcf48f26c01ff4027aa19027efec914ac91c98b7bbf95a06aeb9f4 0.600000000000 1413710 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": 954440, "vin": [ { "gen": { "height": 954430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac091300dcdcf48f26c01ff4027aa19027efec914ac91c98b7bbf95a06aeb9f4" } } ], "extra": [ 1, 26, 42, 49, 33, 94, 47, 131, 154, 50, 168, 139, 253, 176, 189, 101, 230, 42, 212, 252, 58, 155, 17, 100, 104, 254, 134, 245, 48, 108, 29, 167, 91, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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