Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea8db929dc0228bbbc48914fe21726c3216707dac158653f234b7bc007d019b6

Tx prefix hash: 46d1ac5fdedea84a066514fc79529707a4c3e9ca8c41175f463e4c4e8576c4b9
Tx public key: 1e8537b317a6c3adc50286d194cab2b9ded0e191d09f05fc457b76840e4c370c
Timestamp: 1733325409 Timestamp [UCT]: 2024-12-04 15:16:49 Age [y:d:h:m:s]: 00:141:02:02:56
Block: 1167928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100652 RingCT/type: yes/0
Extra: 011e8537b317a6c3adc50286d194cab2b9ded0e191d09f05fc457b76840e4c370c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f6611429b2f444ad40d33a14133ee4d728fb1fd9ca5122281cea09e28260d93 0.600000000000 1653633 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": 1167938, "vin": [ { "gen": { "height": 1167928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f6611429b2f444ad40d33a14133ee4d728fb1fd9ca5122281cea09e28260d93" } } ], "extra": [ 1, 30, 133, 55, 179, 23, 166, 195, 173, 197, 2, 134, 209, 148, 202, 178, 185, 222, 208, 225, 145, 208, 159, 5, 252, 69, 123, 118, 132, 14, 76, 55, 12, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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