Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90e268d284b69818fa3185dc8e45981721038c58769230877e2402961fc385b1

Tx prefix hash: 1d8ae5c5d882fbf48a5ffa1480db9a581a012ff5178cd8b84a5d483fe3c45038
Tx public key: 5e73fcc3ae082bc12875b914e9418dfa7c22f4774bf4cbcad521a7f360f13e29
Timestamp: 1715292705 Timestamp [UCT]: 2024-05-09 22:11:45 Age [y:d:h:m:s]: 00:251:08:46:54
Block: 1018534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179898 RingCT/type: yes/0
Extra: 015e73fcc3ae082bc12875b914e9418dfa7c22f4774bf4cbcad521a7f360f13e290211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1062337f20730e71ab7aed6f504dfdf9b6cfa0b6156a181ef2d19fb47c5cd77a 0.600000000000 1482323 of 15

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": 1018544, "vin": [ { "gen": { "height": 1018534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1062337f20730e71ab7aed6f504dfdf9b6cfa0b6156a181ef2d19fb47c5cd77a" } } ], "extra": [ 1, 94, 115, 252, 195, 174, 8, 43, 193, 40, 117, 185, 20, 233, 65, 141, 250, 124, 34, 244, 119, 75, 244, 203, 202, 213, 33, 167, 243, 96, 241, 62, 41, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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