Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbfe060ae44f265c8ef639d23143decb61f5f4b812b48bed7d2fc899ec8a9fe0

Tx prefix hash: 8b5c768258d3cd6bba09f1fce0c7de52a85a26cfedd6c394c678388e9f9cd54b
Tx public key: 408c40ffcb7475df745b5238b4858d5feeed1ee4d2302c12f233adb7b7c501ac
Timestamp: 1725128280 Timestamp [UCT]: 2024-08-31 18:18:00 Age [y:d:h:m:s]: 01:038:02:56:12
Block: 1100065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285635 RingCT/type: yes/0
Extra: 01408c40ffcb7475df745b5238b4858d5feeed1ee4d2302c12f233adb7b7c501ac021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a31c9e4d1bd5ed91f583ab09c3cea7a22f77d98eae2a17da60bc82d8777486a 0.600000000000 1576038 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": 1100075, "vin": [ { "gen": { "height": 1100065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a31c9e4d1bd5ed91f583ab09c3cea7a22f77d98eae2a17da60bc82d8777486a" } } ], "extra": [ 1, 64, 140, 64, 255, 203, 116, 117, 223, 116, 91, 82, 56, 180, 133, 141, 95, 238, 237, 30, 228, 210, 48, 44, 18, 242, 51, 173, 183, 183, 197, 1, 172, 2, 17, 0, 0, 0, 4, 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