Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb1d13bcf5b5c9e8d6eeebc8d72bbdbd5c61792337851fd37034338a0981f0a0

Tx prefix hash: 969635684a74cdfac0b0eb40d43a5b07ad3e6d02b333130c98dc691f3170e13c
Tx public key: 229d9f3a727f96858438e5c767a0f073e90205a67a0b708a7b2bcead9a02e276
Timestamp: 1632138240 Timestamp [UCT]: 2021-09-20 11:44:00 Age [y:d:h:m:s]: 03:135:17:06:11
Block: 337512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 872749 RingCT/type: yes/0
Extra: 01229d9f3a727f96858438e5c767a0f073e90205a67a0b708a7b2bcead9a02e276021100000082fdc024ec000000000000000000

1 output(s) for total of 46.739393424000 dcy

stealth address amount amount idx
00: 3290c4ff518bf6cbfe0fa0e154731fdb8708717e5b64378991d82cb84e02b802 46.739393424000 694959 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": 337522, "vin": [ { "gen": { "height": 337512 } } ], "vout": [ { "amount": 46739393424, "target": { "key": "3290c4ff518bf6cbfe0fa0e154731fdb8708717e5b64378991d82cb84e02b802" } } ], "extra": [ 1, 34, 157, 159, 58, 114, 127, 150, 133, 132, 56, 229, 199, 103, 160, 240, 115, 233, 2, 5, 166, 122, 11, 112, 138, 123, 43, 206, 173, 154, 2, 226, 118, 2, 17, 0, 0, 0, 130, 253, 192, 36, 236, 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