Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe1cc80cfdb0fac47c47cbf1a6147ef86e5308ddd1d59363d510c983197b1068

Tx prefix hash: 1d89ce810a6a2837cd94dd0e687fb5ca5aa15976f5063af9b0d7aa50d41dd5ad
Tx public key: 8f71e6135f0e73ad9cdd8daea08415038e0036c1a7e02d45bf75eb6ab789b334
Timestamp: 1723899631 Timestamp [UCT]: 2024-08-17 13:00:31 Age [y:d:h:m:s]: 01:167:02:52:24
Block: 1089891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377830 RingCT/type: yes/0
Extra: 018f71e6135f0e73ad9cdd8daea08415038e0036c1a7e02d45bf75eb6ab789b334021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 907c1ebe7eea9a6abc375cf0940a624e69bdf93af62b10af911d8c673ea04335 0.600000000000 1564514 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": 1089901, "vin": [ { "gen": { "height": 1089891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "907c1ebe7eea9a6abc375cf0940a624e69bdf93af62b10af911d8c673ea04335" } } ], "extra": [ 1, 143, 113, 230, 19, 95, 14, 115, 173, 156, 221, 141, 174, 160, 132, 21, 3, 142, 0, 54, 193, 167, 224, 45, 69, 191, 117, 235, 106, 183, 137, 179, 52, 2, 17, 0, 0, 0, 3, 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