Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d43e41b62f8ca4934f10d2ccf9b8a0b0eca655487ace1926f4793d43f742dd3

Tx prefix hash: 778b37613fb3bb975e2a969ece15d10ecbed055e82184c4b486706f65c36af99
Tx public key: dfc3827a4dbbc989bf40e179127b10941356cf48a874e3c59b72fae28d31236f
Timestamp: 1578425169 Timestamp [UCT]: 2020-01-07 19:26:09 Age [y:d:h:m:s]: 05:047:21:20:14
Block: 40732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184178 RingCT/type: yes/0
Extra: 01dfc3827a4dbbc989bf40e179127b10941356cf48a874e3c59b72fae28d31236f021100000001dcee4b4d000000000000000000

1 output(s) for total of 449.820062843000 dcy

stealth address amount amount idx
00: 0c7aa501e345cb941bcabe43cc9fd9c57701cbecda84b5eba05b66b329eab8ac 449.820062843000 71817 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": 40742, "vin": [ { "gen": { "height": 40732 } } ], "vout": [ { "amount": 449820062843, "target": { "key": "0c7aa501e345cb941bcabe43cc9fd9c57701cbecda84b5eba05b66b329eab8ac" } } ], "extra": [ 1, 223, 195, 130, 122, 77, 187, 201, 137, 191, 64, 225, 121, 18, 123, 16, 148, 19, 86, 207, 72, 168, 116, 227, 197, 155, 114, 250, 226, 141, 49, 35, 111, 2, 17, 0, 0, 0, 1, 220, 238, 75, 77, 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