Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 400353b4c8fea9e8cdd9a3ff54282c78fc96bd20cf45bb97562146b07cb64e0a

Tx prefix hash: cb786f418de94ea0421d16e025f53880da067520f1744fe0f4653e93af4dd733
Tx public key: 548abe4f03f819f0ae994aeaf5ca53c45c80f03ca0168202ca1c336eb8705c39
Timestamp: 1580786507 Timestamp [UCT]: 2020-02-04 03:21:47 Age [y:d:h:m:s]: 04:291:05:07:49
Block: 58108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1099588 RingCT/type: yes/0
Extra: 01548abe4f03f819f0ae994aeaf5ca53c45c80f03ca0168202ca1c336eb8705c390211000000058a2ee0d9000000000000000000

1 output(s) for total of 393.971581043000 dcy

stealth address amount amount idx
00: ee42316ab98e37efe4ac5f40ee0f19212924ae66e11f865c2802d7172b6ac52d 393.971581043000 107442 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": 58118, "vin": [ { "gen": { "height": 58108 } } ], "vout": [ { "amount": 393971581043, "target": { "key": "ee42316ab98e37efe4ac5f40ee0f19212924ae66e11f865c2802d7172b6ac52d" } } ], "extra": [ 1, 84, 138, 190, 79, 3, 248, 25, 240, 174, 153, 74, 234, 245, 202, 83, 196, 92, 128, 240, 60, 160, 22, 130, 2, 202, 28, 51, 110, 184, 112, 92, 57, 2, 17, 0, 0, 0, 5, 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