Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ded5a06e12f652c4fb3f45d77cdd46486d4fce8e6740411fa8b1f6a0840e252c

Tx prefix hash: e1859dfbacd8b04b5e6bb2f84b4ee4e17b1a92ba34f6d654d81983bcc0e4b3af
Tx public key: 30c4f5efef0820d3426e54c69374386358d2dc5c73a51df7e35074843c458ba2
Timestamp: 1725212012 Timestamp [UCT]: 2024-09-01 17:33:32 Age [y:d:h:m:s]: 00:083:20:12:03
Block: 1100769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59956 RingCT/type: yes/0
Extra: 0130c4f5efef0820d3426e54c69374386358d2dc5c73a51df7e35074843c458ba2021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 762f74789602d9986d5e8d2e9ecf347f0e572496f6175a3ee18c8d1eb7840dc9 0.600000000000 1576750 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": 1100779, "vin": [ { "gen": { "height": 1100769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "762f74789602d9986d5e8d2e9ecf347f0e572496f6175a3ee18c8d1eb7840dc9" } } ], "extra": [ 1, 48, 196, 245, 239, 239, 8, 32, 211, 66, 110, 84, 198, 147, 116, 56, 99, 88, 210, 220, 92, 115, 165, 29, 247, 227, 80, 116, 132, 60, 69, 139, 162, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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