Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3acabb05c77c63ad5dd8a244f41c60e83b1c8c451f0ed545ba495cc1fac1b69

Tx prefix hash: d04538512a07a7e125b17ca4bca9b3ab42bc236f9df03da92c9d52db207d8352
Tx public key: f438c36160a62afb52988a2e85cf73c432557bd897fe206f0fa3f503e7f1a6a6
Timestamp: 1725016702 Timestamp [UCT]: 2024-08-30 11:18:22 Age [y:d:h:m:s]: 00:257:08:28:44
Block: 1099147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183816 RingCT/type: yes/0
Extra: 01f438c36160a62afb52988a2e85cf73c432557bd897fe206f0fa3f503e7f1a6a602110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa31da17df76aee025a841fdd7239849ca7483318172abbcaf023ebf3c675263 0.600000000000 1575074 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": 1099157, "vin": [ { "gen": { "height": 1099147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa31da17df76aee025a841fdd7239849ca7483318172abbcaf023ebf3c675263" } } ], "extra": [ 1, 244, 56, 195, 97, 96, 166, 42, 251, 82, 152, 138, 46, 133, 207, 115, 196, 50, 85, 123, 216, 151, 254, 32, 111, 15, 163, 245, 3, 231, 241, 166, 166, 2, 17, 0, 0, 0, 15, 145, 225, 60, 4, 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