Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac0209167dc57a4d89e4cd042893d14c46cf87f9e31efd5de43393ece59a241f

Tx prefix hash: 153ef066e4c74fece710f449194082e0100232af59fbfc9d6fa38b309f4ce50e
Tx public key: 9e7f2aba94866daebb4882d9af620699b60d90712ed2544ab3a0afe7fe57cf9f
Timestamp: 1695119460 Timestamp [UCT]: 2023-09-19 10:31:00 Age [y:d:h:m:s]: 01:158:06:17:12
Block: 851473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374151 RingCT/type: yes/0
Extra: 019e7f2aba94866daebb4882d9af620699b60d90712ed2544ab3a0afe7fe57cf9f02110000000f4b8f5122000000000000000000

1 output(s) for total of 0.926265092000 dcy

stealth address amount amount idx
00: 0f4286eac7e826e43120902d0d70598d8deaa7c78ab1e44e0e9d66d551df78f8 0.926265092000 1305255 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": 851483, "vin": [ { "gen": { "height": 851473 } } ], "vout": [ { "amount": 926265092, "target": { "key": "0f4286eac7e826e43120902d0d70598d8deaa7c78ab1e44e0e9d66d551df78f8" } } ], "extra": [ 1, 158, 127, 42, 186, 148, 134, 109, 174, 187, 72, 130, 217, 175, 98, 6, 153, 182, 13, 144, 113, 46, 210, 84, 74, 179, 160, 175, 231, 254, 87, 207, 159, 2, 17, 0, 0, 0, 15, 75, 143, 81, 34, 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