Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c87c7c6788e7add3e07a8b4099475906b89c5ed167dc6d5e45b2257a9758ead1

Tx prefix hash: 0fe64423b5c9af2725278a46d0911c6999de7cfd7f43e4747fc116488f8b9457
Tx public key: a7037deb858cafd1060fb7ec1041b592f9ed8788bc1ddf7956a39b0c5dd15c4d
Timestamp: 1685566131 Timestamp [UCT]: 2023-05-31 20:48:51 Age [y:d:h:m:s]: 01:233:17:36:28
Block: 772330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428433 RingCT/type: yes/0
Extra: 01a7037deb858cafd1060fb7ec1041b592f9ed8788bc1ddf7956a39b0c5dd15c4d02110000000375e3f0e9000000000000000000

1 output(s) for total of 1.694143801000 dcy

stealth address amount amount idx
00: 657d39539dd32b38b84e4a8d77789dd1e4cf03ecef3c92e992f48644aa401bd5 1.694143801000 1221727 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": 772340, "vin": [ { "gen": { "height": 772330 } } ], "vout": [ { "amount": 1694143801, "target": { "key": "657d39539dd32b38b84e4a8d77789dd1e4cf03ecef3c92e992f48644aa401bd5" } } ], "extra": [ 1, 167, 3, 125, 235, 133, 140, 175, 209, 6, 15, 183, 236, 16, 65, 181, 146, 249, 237, 135, 136, 188, 29, 223, 121, 86, 163, 155, 12, 93, 209, 92, 77, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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