Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73541f9ddc2094d3bf5bd5cf524b342bddfd79404204593596da700ae18aa79a

Tx prefix hash: 0101e4c50da0f26d37831bcf5f66d4b8ebe9d389d2244c3cc4cc1dd2544e2f1b
Tx public key: 7a1fc4b222cda1b209f1d1c5a508525b1b9a5199cb34a83679d53f0acc2ce59e
Timestamp: 1674788210 Timestamp [UCT]: 2023-01-27 02:56:50 Age [y:d:h:m:s]: 02:097:05:09:30
Block: 683604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 591137 RingCT/type: yes/0
Extra: 017a1fc4b222cda1b209f1d1c5a508525b1b9a5199cb34a83679d53f0acc2ce59e0211000000015029cbac000000000000000000

1 output(s) for total of 3.333773636000 dcy

stealth address amount amount idx
00: 23898df3988f3d242a254df942aefd7f33a50d2d29fa72bec08986c824d1d425 3.333773636000 1125799 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": 683614, "vin": [ { "gen": { "height": 683604 } } ], "vout": [ { "amount": 3333773636, "target": { "key": "23898df3988f3d242a254df942aefd7f33a50d2d29fa72bec08986c824d1d425" } } ], "extra": [ 1, 122, 31, 196, 178, 34, 205, 161, 178, 9, 241, 209, 197, 165, 8, 82, 91, 27, 154, 81, 153, 203, 52, 168, 54, 121, 213, 63, 10, 204, 44, 229, 158, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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