Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c57e5ff14d9935c525ead8d4434095cceb32a66bdc4917d81f08e10062efcac

Tx prefix hash: 781f58fafdef9d9c3adf15dec4b477d2279a2e96d721fc38ed48ff0da2a4a5d6
Tx public key: 6781e51a469bc2f6e56d340c62a096ff78843c74f4f98efb8c51928959d4caf3
Timestamp: 1723915646 Timestamp [UCT]: 2024-08-17 17:27:26 Age [y:d:h:m:s]: 00:189:04:52:03
Block: 1090024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135048 RingCT/type: yes/0
Extra: 016781e51a469bc2f6e56d340c62a096ff78843c74f4f98efb8c51928959d4caf3021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c06af7a660cf2d61d83c3c4667be7e62458ad0384454c3f100623358fa3eb36 0.600000000000 1564647 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": 1090034, "vin": [ { "gen": { "height": 1090024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c06af7a660cf2d61d83c3c4667be7e62458ad0384454c3f100623358fa3eb36" } } ], "extra": [ 1, 103, 129, 229, 26, 70, 155, 194, 246, 229, 109, 52, 12, 98, 160, 150, 255, 120, 132, 60, 116, 244, 249, 142, 251, 140, 81, 146, 137, 89, 212, 202, 243, 2, 17, 0, 0, 0, 2, 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