Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a6a16e171630c28f5d846d0174fea338a279b280c442cfa389e116a75212a60

Tx prefix hash: 1a5108405e8a2448269985b8a96ac6c637f2c82a8c4dca10b306f6be2fea9571
Tx public key: 9175dbf932b00c00ea1259b65476cffb299fff0acef839a7cd4a5d5d92cd5ffc
Timestamp: 1580485421 Timestamp [UCT]: 2020-01-31 15:43:41 Age [y:d:h:m:s]: 04:301:06:52:26
Block: 55925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106494 RingCT/type: yes/0
Extra: 019175dbf932b00c00ea1259b65476cffb299fff0acef839a7cd4a5d5d92cd5ffc0211000000042264afe6000000000000000000

1 output(s) for total of 400.588136778000 dcy

stealth address amount amount idx
00: 534e844296df8d05576f07f803a3f614f90d64e04f85ae86d2b31a48a2191cef 400.588136778000 103162 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": 55935, "vin": [ { "gen": { "height": 55925 } } ], "vout": [ { "amount": 400588136778, "target": { "key": "534e844296df8d05576f07f803a3f614f90d64e04f85ae86d2b31a48a2191cef" } } ], "extra": [ 1, 145, 117, 219, 249, 50, 176, 12, 0, 234, 18, 89, 182, 84, 118, 207, 251, 41, 159, 255, 10, 206, 248, 57, 167, 205, 74, 93, 93, 146, 205, 95, 252, 2, 17, 0, 0, 0, 4, 34, 100, 175, 230, 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