Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 116add37745ed3bc35f4b08a0f268235756e30b97feb530c662d88f9415e7857

Tx prefix hash: c19c5056af4fa9aa892c86e952b51e5c5c4a7be1e42ef8f6430487f0daf31ab5
Tx public key: b712b2a670a240cc3ae94347ed200e1dcc816b277b5e1393403dc9a4a314ae48
Timestamp: 1578638405 Timestamp [UCT]: 2020-01-10 06:40:05 Age [y:d:h:m:s]: 05:141:22:43:58
Block: 42282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1251693 RingCT/type: yes/0
Extra: 01b712b2a670a240cc3ae94347ed200e1dcc816b277b5e1393403dc9a4a314ae480211000000addcee4b4d000000000000000000

1 output(s) for total of 444.531996644000 dcy

stealth address amount amount idx
00: 0657e0ec95dada66f6668e60543e1e051cf453681a7ab53aebf95ed3484dfd1b 444.531996644000 76098 of 0

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": 42292, "vin": [ { "gen": { "height": 42282 } } ], "vout": [ { "amount": 444531996644, "target": { "key": "0657e0ec95dada66f6668e60543e1e051cf453681a7ab53aebf95ed3484dfd1b" } } ], "extra": [ 1, 183, 18, 178, 166, 112, 162, 64, 204, 58, 233, 67, 71, 237, 32, 14, 29, 204, 129, 107, 39, 123, 94, 19, 147, 64, 61, 201, 164, 163, 20, 174, 72, 2, 17, 0, 0, 0, 173, 220, 238, 75, 77, 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