Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e00f4ae2f35c4d0951bc9900512aba4cab4ed39350745be472d76e1588369e2

Tx prefix hash: 610f5759124123d141f2eb0a4c46cc8a5cb94712f08a373dbd21062a2274db2b
Tx public key: 6960698d4830f7adec5c7f5b6be3179e3fb66d7db8ddc60916a3a7ed2324b002
Timestamp: 1725726335 Timestamp [UCT]: 2024-09-07 16:25:35 Age [y:d:h:m:s]: 00:215:11:05:50
Block: 1105033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153836 RingCT/type: yes/0
Extra: 016960698d4830f7adec5c7f5b6be3179e3fb66d7db8ddc60916a3a7ed2324b00202110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c55ff56aefdcc57b8e31f79f6b47e29bfdf3f7f79eaff95ab17120d13f880df 0.600000000000 1582370 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": 1105043, "vin": [ { "gen": { "height": 1105033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c55ff56aefdcc57b8e31f79f6b47e29bfdf3f7f79eaff95ab17120d13f880df" } } ], "extra": [ 1, 105, 96, 105, 141, 72, 48, 247, 173, 236, 92, 127, 91, 107, 227, 23, 158, 63, 182, 109, 125, 184, 221, 198, 9, 22, 163, 167, 237, 35, 36, 176, 2, 2, 17, 0, 0, 0, 12, 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