Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e65dda0279c17bc925ada5f3c0c97f0e633167130af772389873e201cc767aaa

Tx prefix hash: b85d8307a35d026a71319e729bd47ec5313deac0da262602241216ff55043083
Tx public key: 52a091b0c0e8470a6c64d43588c3cc8b473ac1f1cd0cd487aa4c3c4171082dd2
Timestamp: 1682533361 Timestamp [UCT]: 2023-04-26 18:22:41 Age [y:d:h:m:s]: 01:271:13:16:10
Block: 747185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455529 RingCT/type: yes/0
Extra: 0152a091b0c0e8470a6c64d43588c3cc8b473ac1f1cd0cd487aa4c3c4171082dd20211000000017e406890000000000000000000

1 output(s) for total of 2.052419494000 dcy

stealth address amount amount idx
00: 1e13ea1aae4443e3d3e588c66976c5a9b6ccf044ab973423f4bc8ac8aa0ee337 2.052419494000 1194830 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": 747195, "vin": [ { "gen": { "height": 747185 } } ], "vout": [ { "amount": 2052419494, "target": { "key": "1e13ea1aae4443e3d3e588c66976c5a9b6ccf044ab973423f4bc8ac8aa0ee337" } } ], "extra": [ 1, 82, 160, 145, 176, 192, 232, 71, 10, 108, 100, 212, 53, 136, 195, 204, 139, 71, 58, 193, 241, 205, 12, 212, 135, 170, 76, 60, 65, 113, 8, 45, 210, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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