Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 519e90473b4f1bb83dd8d7086fb4390245b10c7aad3ea7e9523ba0218e7132dc

Tx prefix hash: ffeb1cd723e60af2aa13ba4029f1d339b9e44e5251a40d9429589915d90fe87d
Tx public key: 0f734b3c9de2e2288030a706e946e346058a8a40d96f6e4aa676458d132b1429
Timestamp: 1735843608 Timestamp [UCT]: 2025-01-02 18:46:48 Age [y:d:h:m:s]: 00:323:05:35:12
Block: 1188774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228533 RingCT/type: yes/0
Extra: 010f734b3c9de2e2288030a706e946e346058a8a40d96f6e4aa676458d132b1429021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 383d9a295761e18957421651f41e3813a6a20ec31333dad3118f53529fe1da34 0.600000000000 1675277 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": 1188784, "vin": [ { "gen": { "height": 1188774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "383d9a295761e18957421651f41e3813a6a20ec31333dad3118f53529fe1da34" } } ], "extra": [ 1, 15, 115, 75, 60, 157, 226, 226, 40, 128, 48, 167, 6, 233, 70, 227, 70, 5, 138, 138, 64, 217, 111, 110, 74, 166, 118, 69, 141, 19, 43, 20, 41, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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