Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c9f6f563f137b265f6ea22b857a22ae69d4022a28d2853468d54f1c942c9c78

Tx prefix hash: 4dac9c5524f3f3bf58920f69f4f158dd5c76d301eb07dcc7fa9653d2d4b88047
Tx public key: b8b5cf5da91842b4bd42f54251be24b3c7f921b443873473611ca2d052c21aee
Timestamp: 1724359970 Timestamp [UCT]: 2024-08-22 20:52:50 Age [y:d:h:m:s]: 00:226:16:06:33
Block: 1093714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161846 RingCT/type: yes/0
Extra: 01b8b5cf5da91842b4bd42f54251be24b3c7f921b443873473611ca2d052c21aee021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 084fa33684bef538b720021e029addfa53f55ef28ccc7615a3f1c677796f4120 0.600000000000 1568711 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": 1093724, "vin": [ { "gen": { "height": 1093714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "084fa33684bef538b720021e029addfa53f55ef28ccc7615a3f1c677796f4120" } } ], "extra": [ 1, 184, 181, 207, 93, 169, 24, 66, 180, 189, 66, 245, 66, 81, 190, 36, 179, 199, 249, 33, 180, 67, 135, 52, 115, 97, 28, 162, 208, 82, 194, 26, 238, 2, 17, 0, 0, 0, 8, 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