Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 498bd02c59f9167d37553b69f3f8c7eeb588ed6ef12a7a3e2688f17740e44c12

Tx prefix hash: ea50d021fb03a50f18bc61645d386195b913cdfa5ab241f0f2fbb126f649e4bf
Tx public key: ce8708e3fa61e9376bd5472c6a7a309400e7b7f4dded756f69cd3f2671e7a486
Timestamp: 1700425603 Timestamp [UCT]: 2023-11-19 20:26:43 Age [y:d:h:m:s]: 02:006:09:55:13
Block: 895273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524362 RingCT/type: yes/0
Extra: 01ce8708e3fa61e9376bd5472c6a7a309400e7b7f4dded756f69cd3f2671e7a486021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.663115067000 dcy

stealth address amount amount idx
00: aecb1ffd68ce24d18356f1777f99af334b0af82fb6468c4572d3b2d2002e201f 0.663115067000 1351502 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": 895283, "vin": [ { "gen": { "height": 895273 } } ], "vout": [ { "amount": 663115067, "target": { "key": "aecb1ffd68ce24d18356f1777f99af334b0af82fb6468c4572d3b2d2002e201f" } } ], "extra": [ 1, 206, 135, 8, 227, 250, 97, 233, 55, 107, 213, 71, 44, 106, 122, 48, 148, 0, 231, 183, 244, 221, 237, 117, 111, 105, 205, 63, 38, 113, 231, 164, 134, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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