Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9cc8e01c12051224dc8e3c5d8c43b69f5d922ab511ee5ccd796f9e1d6b92ffd

Tx prefix hash: 52d806025e3cd20059f7f19300e789f9e631901f7c3a89c61b8d25219aec36e2
Tx public key: f0c69975be1dc403a9448c05bdcfdcba369dca6080b8fe3538d9bdcfe54c9045
Timestamp: 1735353858 Timestamp [UCT]: 2024-12-28 02:44:18 Age [y:d:h:m:s]: 00:116:14:33:50
Block: 1184720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83132 RingCT/type: yes/0
Extra: 01f0c69975be1dc403a9448c05bdcfdcba369dca6080b8fe3538d9bdcfe54c904502110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4c6f4e280a228a0c48a3eb1c7c756e1bfeb1ffa40e7824923e17bb98f56d82a 0.600000000000 1671179 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": 1184730, "vin": [ { "gen": { "height": 1184720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4c6f4e280a228a0c48a3eb1c7c756e1bfeb1ffa40e7824923e17bb98f56d82a" } } ], "extra": [ 1, 240, 198, 153, 117, 190, 29, 196, 3, 169, 68, 140, 5, 189, 207, 220, 186, 54, 157, 202, 96, 128, 184, 254, 53, 56, 217, 189, 207, 229, 76, 144, 69, 2, 17, 0, 0, 0, 10, 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