Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b36f62ac7398c80e068884cca59ea616319afa39e373f568f73d81c5a08382f

Tx prefix hash: ebb84b05dfb4bccb3334cbd6cb8013b248191d0df9c2bcfaec9da1579955c645
Tx public key: 64b36c514d93e66d0f862a8f6646de7f5f2ab09db873408f5877b6e52d0a25b2
Timestamp: 1695995704 Timestamp [UCT]: 2023-09-29 13:55:04 Age [y:d:h:m:s]: 01:238:23:36:56
Block: 858747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431904 RingCT/type: yes/0
Extra: 0164b36c514d93e66d0f862a8f6646de7f5f2ab09db873408f5877b6e52d0a25b2021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.876223204000 dcy

stealth address amount amount idx
00: c09eaf993e268166545210aa409c11b0d291ea80f3131c90cc41ab0f151aed7c 0.876223204000 1312937 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": 858757, "vin": [ { "gen": { "height": 858747 } } ], "vout": [ { "amount": 876223204, "target": { "key": "c09eaf993e268166545210aa409c11b0d291ea80f3131c90cc41ab0f151aed7c" } } ], "extra": [ 1, 100, 179, 108, 81, 77, 147, 230, 109, 15, 134, 42, 143, 102, 70, 222, 127, 95, 42, 176, 157, 184, 115, 64, 143, 88, 119, 182, 229, 45, 10, 37, 178, 2, 17, 0, 0, 0, 6, 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