Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20725195d31cb094eaf2d4e61d7a662f56ac74e60e5f519fdd506fe0a14919b5

Tx prefix hash: 890688804e09cfcb0ad3d5ed1d3760e29dc1043d0f443bcb8a04661a6523e2f7
Tx public key: 75a4b45cc697c7dd3a23d9ec0acfec91f2623d7959e4cded331dd964709640be
Timestamp: 1687066104 Timestamp [UCT]: 2023-06-18 05:28:24 Age [y:d:h:m:s]: 01:215:02:13:29
Block: 784764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415125 RingCT/type: yes/0
Extra: 0175a4b45cc697c7dd3a23d9ec0acfec91f2623d7959e4cded331dd964709640be021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.540817666000 dcy

stealth address amount amount idx
00: 170c1c09525971a2dd4419a3b7583cd15dde0df9287ea30a2d3d201fbdff75e0 1.540817666000 1234665 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": 784774, "vin": [ { "gen": { "height": 784764 } } ], "vout": [ { "amount": 1540817666, "target": { "key": "170c1c09525971a2dd4419a3b7583cd15dde0df9287ea30a2d3d201fbdff75e0" } } ], "extra": [ 1, 117, 164, 180, 92, 198, 151, 199, 221, 58, 35, 217, 236, 10, 207, 236, 145, 242, 98, 61, 121, 89, 228, 205, 237, 51, 29, 217, 100, 112, 150, 64, 190, 2, 17, 0, 0, 0, 2, 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