Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b837e9e014a10da0f02fd01d32d8ef7614348582fd516be3423089aed73e5a1

Tx prefix hash: ef7bb7e54e75f4e9c17e0e0b2a4e582a6429164509a0033a2b360d1596bb7fcb
Tx public key: 4a130d3f419009a64297fe2f2ef309a47cb9f796f3ea5ade923a6b337fe19a19
Timestamp: 1579296621 Timestamp [UCT]: 2020-01-17 21:30:21 Age [y:d:h:m:s]: 05:313:09:07:23
Block: 47853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1371791 RingCT/type: yes/0
Extra: 014a130d3f419009a64297fe2f2ef309a47cb9f796f3ea5ade923a6b337fe19a190211000000068a2ee0d9000000000000000000

1 output(s) for total of 426.033727957000 dcy

stealth address amount amount idx
00: f43a567d98fcc57395fe207c4f90682d7235121b01145f5e59c1b5c05dc27da7 426.033727957000 88406 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": 47863, "vin": [ { "gen": { "height": 47853 } } ], "vout": [ { "amount": 426033727957, "target": { "key": "f43a567d98fcc57395fe207c4f90682d7235121b01145f5e59c1b5c05dc27da7" } } ], "extra": [ 1, 74, 19, 13, 63, 65, 144, 9, 166, 66, 151, 254, 47, 46, 243, 9, 164, 124, 185, 247, 150, 243, 234, 90, 222, 146, 58, 107, 51, 127, 225, 154, 25, 2, 17, 0, 0, 0, 6, 138, 46, 224, 217, 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