Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3aeaab0fe6b4bea69b6448c84c42517798d7123459a64dfe491e9979a7d14c2

Tx prefix hash: 777567d3579be0464ad2d6a4131fd603f3baf903c4c8d9975a70a0f6a8adf9b5
Tx public key: fd91f0f956f1d105856a38279e92d5d355039a31b4d3211a4da2946a361523f2
Timestamp: 1578930170 Timestamp [UCT]: 2020-01-13 15:42:50 Age [y:d:h:m:s]: 05:121:14:10:57
Block: 44774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1237049 RingCT/type: yes/0
Extra: 01fd91f0f956f1d105856a38279e92d5d355039a31b4d3211a4da2946a361523f202110000000e4ac5aa02000000000000000000

1 output(s) for total of 436.160158591000 dcy

stealth address amount amount idx
00: 1f915bfe734ddcb92482fb1947d307e889dbde1985c5daf4efa9a2db5e4681a0 436.160158591000 81561 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": 44784, "vin": [ { "gen": { "height": 44774 } } ], "vout": [ { "amount": 436160158591, "target": { "key": "1f915bfe734ddcb92482fb1947d307e889dbde1985c5daf4efa9a2db5e4681a0" } } ], "extra": [ 1, 253, 145, 240, 249, 86, 241, 209, 5, 133, 106, 56, 39, 158, 146, 213, 211, 85, 3, 154, 49, 180, 211, 33, 26, 77, 162, 148, 106, 54, 21, 35, 242, 2, 17, 0, 0, 0, 14, 74, 197, 170, 2, 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