Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0137dcaddb13595369d2f18d285b9994454365fe6a65665b1d378b0b375d86a2

Tx prefix hash: 6845766eb4501c9f9f26010c7610002fca9aaa5f6f41ead6952542e09b62ecd4
Tx public key: 9ac6c5d28dade30dd0d04c9cc62094712be5aa1f57c06b15dbfb694a5f57c68c
Timestamp: 1705118639 Timestamp [UCT]: 2024-01-13 04:03:59 Age [y:d:h:m:s]: 01:073:09:45:44
Block: 934162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313560 RingCT/type: yes/0
Extra: 019ac6c5d28dade30dd0d04c9cc62094712be5aa1f57c06b15dbfb694a5f57c68c02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4199caa85eb1bef51fb816e12f9c2192c50c86170c81d91ecc0eb903d128c9aa 0.600000000000 1392150 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": 934172, "vin": [ { "gen": { "height": 934162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4199caa85eb1bef51fb816e12f9c2192c50c86170c81d91ecc0eb903d128c9aa" } } ], "extra": [ 1, 154, 198, 197, 210, 141, 173, 227, 13, 208, 208, 76, 156, 198, 32, 148, 113, 43, 229, 170, 31, 87, 192, 107, 21, 219, 251, 105, 74, 95, 87, 198, 140, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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