Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e214c68472497018514289d3a0b586d978dacfe61e1fc224fc4b2f1fdf08a4e6

Tx prefix hash: 4d64f665865d3c9708618330e5736a380f5585e11b953f7011bb899df5c975dd
Tx public key: 5495866a2ddaa8982c933d493b533383ac3b9ba1097ad8ae932c6612ca565f40
Timestamp: 1673967338 Timestamp [UCT]: 2023-01-17 14:55:38 Age [y:d:h:m:s]: 01:302:22:27:46
Block: 676780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477487 RingCT/type: yes/0
Extra: 015495866a2ddaa8982c933d493b533383ac3b9ba1097ad8ae932c6612ca565f400211000000038b7b6602000000000000000000

1 output(s) for total of 3.511938181000 dcy

stealth address amount amount idx
00: 2e8264e573c4f795645b2f827fc4257ca968f2b7e711a1ebc43b921eead810a8 3.511938181000 1118509 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": 676790, "vin": [ { "gen": { "height": 676780 } } ], "vout": [ { "amount": 3511938181, "target": { "key": "2e8264e573c4f795645b2f827fc4257ca968f2b7e711a1ebc43b921eead810a8" } } ], "extra": [ 1, 84, 149, 134, 106, 45, 218, 168, 152, 44, 147, 61, 73, 59, 83, 51, 131, 172, 59, 155, 161, 9, 122, 216, 174, 147, 44, 102, 18, 202, 86, 95, 64, 2, 17, 0, 0, 0, 3, 139, 123, 102, 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