Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c114e347e3db3526c368c768ffc7a71d54ad82d51f95a69da466bf14b4dcf2a

Tx prefix hash: 70924959f2398d90fec5eaf7348c0c33478c73162f4f6e315dd22765215834b3
Tx public key: 3c994ffbb99f6e4118dac9382d3954d022908fb7c6f4a4d828e9a758f74bed03
Timestamp: 1705277613 Timestamp [UCT]: 2024-01-15 00:13:33 Age [y:d:h:m:s]: 01:093:05:15:12
Block: 935479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327724 RingCT/type: yes/0
Extra: 013c994ffbb99f6e4118dac9382d3954d022908fb7c6f4a4d828e9a758f74bed0302110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f49f1d9c2c7cf5212e23f215178b5849d5197ee6ac09d20ff89a1401f8ede830 0.600000000000 1393495 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": 935489, "vin": [ { "gen": { "height": 935479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f49f1d9c2c7cf5212e23f215178b5849d5197ee6ac09d20ff89a1401f8ede830" } } ], "extra": [ 1, 60, 153, 79, 251, 185, 159, 110, 65, 24, 218, 201, 56, 45, 57, 84, 208, 34, 144, 143, 183, 198, 244, 164, 216, 40, 233, 167, 88, 247, 75, 237, 3, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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