Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f358e53d33a7a96e3bb80491ed05d09562ad67c9efd5d4590032e0f10b30115

Tx prefix hash: 55fff72b667f2b0664d067d19ccb4ccb21d13c4ac8c2f80ba96ff636106603e1
Tx public key: dfcb320bc3b9eac3fa6544902d8883a5a31dd3ce335e05d1fa61a1816ad16a9e
Timestamp: 1720864011 Timestamp [UCT]: 2024-07-13 09:46:51 Age [y:d:h:m:s]: 00:245:05:08:32
Block: 1064734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175182 RingCT/type: yes/0
Extra: 01dfcb320bc3b9eac3fa6544902d8883a5a31dd3ce335e05d1fa61a1816ad16a9e02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 205f61717585652231b5c7b50659b16b9e70a1dfb36d7d558ad4a21d5644a607 0.600000000000 1535269 of 15

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": 1064744, "vin": [ { "gen": { "height": 1064734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "205f61717585652231b5c7b50659b16b9e70a1dfb36d7d558ad4a21d5644a607" } } ], "extra": [ 1, 223, 203, 50, 11, 195, 185, 234, 195, 250, 101, 68, 144, 45, 136, 131, 165, 163, 29, 211, 206, 51, 94, 5, 209, 250, 97, 161, 129, 106, 209, 106, 158, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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