Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 010d0359712afd101c63b2f8f310ccd4e1eb2da268c6ab0412bffec6341c4976

Tx prefix hash: c54800a82ae0c0f7d20568898a3e1fcdd1eb9286aae59a60d14d10154f9cf15d
Tx public key: d1c01480edc802d65586ad0772e8c0ed1884c7b14ee6b180f0bea3ee6cddd531
Timestamp: 1735013709 Timestamp [UCT]: 2024-12-24 04:15:09 Age [y:d:h:m:s]: 00:089:00:11:59
Block: 1181914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63399 RingCT/type: yes/0
Extra: 01d1c01480edc802d65586ad0772e8c0ed1884c7b14ee6b180f0bea3ee6cddd5310211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f49bb1f4fd28e83d91081be6e29d648a35bd389451ab906916f340fccef37c0 0.600000000000 1668343 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": 1181924, "vin": [ { "gen": { "height": 1181914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f49bb1f4fd28e83d91081be6e29d648a35bd389451ab906916f340fccef37c0" } } ], "extra": [ 1, 209, 192, 20, 128, 237, 200, 2, 214, 85, 134, 173, 7, 114, 232, 192, 237, 24, 132, 199, 177, 78, 230, 177, 128, 240, 190, 163, 238, 108, 221, 213, 49, 2, 17, 0, 0, 0, 2, 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