Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd1646060e4c35fdc86e66cd61851caf70acee01b36e0acb9e0b864a3dcb0924

Tx prefix hash: 627ffe7f3457484042d64e9f19e0c0e124d85dcd2ab80c9950edff989920aab6
Tx public key: 58e685a2f3dce54f9df3fb9d3989530147bcf7b1b1a9ef4a00cf7af4eac9cf7f
Timestamp: 1739188077 Timestamp [UCT]: 2025-02-10 11:47:57 Age [y:d:h:m:s]: 00:355:06:30:59
Block: 1216198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251584 RingCT/type: yes/0
Extra: 0158e685a2f3dce54f9df3fb9d3989530147bcf7b1b1a9ef4a00cf7af4eac9cf7f0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc328cc8feaf273c5f0b3f66ed3256595188f861ccc9deaadd48147c3ea1afa2 0.600000000000 1702999 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": 1216208, "vin": [ { "gen": { "height": 1216198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc328cc8feaf273c5f0b3f66ed3256595188f861ccc9deaadd48147c3ea1afa2" } } ], "extra": [ 1, 88, 230, 133, 162, 243, 220, 229, 79, 157, 243, 251, 157, 57, 137, 83, 1, 71, 188, 247, 177, 177, 169, 239, 74, 0, 207, 122, 244, 234, 201, 207, 127, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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